Current Behavior

@nx/js:typescript-sync decides which projects belong in the root tsconfig.json references from the project graph alone. It never consults the include/exclude on the @nx/js/typescript plugin's own nx.json registrations, so a project the plugin was explicitly told to skip can still be demanded as a root reference.

This repo already declares that intent:

{
  "plugin": "@nx/js/typescript",
  "exclude": ["examples/angular-rspack/**/*", "examples/react/**/*", "nx-dev/**/*", "e2e/**/*"]
}

Yet adding "composite": true to examples/react/basic/tsconfig.base.json and running nx sync:check reports the workspace out of sync, demanding root references for 13 example projects. Those examples are deliberately standalone pnpm workspaces — own lockfile, own install, link: deps — so referencing them couples the parent repo's tsc --build to a separately installed workspace.

A second, independent bug makes the report misleading. changedFiles, which drives both the out-of-sync verdict and the message, is populated before the composite filter is applied — the filter only runs when deciding what to write. So 12 of those 13 entries were phantom: the angular-rspack examples are not composite and would never have been written. Only examples/react/basic was ever a real candidate.

Expected Behavior

Sync only considers projects the plugin actually manages, and only reports references it could actually write.

Candidates are filtered through findMatchingConfigFiles — the same matcher Nx uses to decide which files a plugin's createNodes sees — so sync and inference agree by construction rather than via two glob implementations that can drift. Matching is against the tsconfig path, since plugin patterns like examples/react/**/* are written against files.

Three behaviors worth calling out:

• Registrations are additive. This repo has two: the first excludes e2e/**/*, the second includes it. A single-registration read would have dropped every e2e project's reference.
• It fails open. A bare string registration ("@nx/js/typescript") or no registration at all filters nothing. This is core behavior for every Nx workspace, and narrowing on absent config would be a silent regression.
• The composite check moved into the first pass, so an unsatisfiable reference is never reported as the reason a workspace is out of sync.

Verification

Two of the five new tests fail without the fix — one per bug. The other three are regression guards proving the filter doesn't over-filter (second registration, bare string, unregistered plugin); those pass either way by design.

End-to-end against this repo, with composite: true added to examples/react/basic:

nx run-many -t lint,test -p js passes — 821 tests, including the 43 pre-existing typescript-sync specs.

Note that nx sync:check in this repo runs the published @nx/js, so it cannot exercise this change until release; the A/B above drives the built generator directly against the real workspace.

Related Issue(s)

Fixes NXC-4734

View session information ↗